Skip to content

Conversation

@vishwa-uber
Copy link
Contributor

@vishwa-uber vishwa-uber commented Oct 28, 2025

Whats new

Screenshot 2025-10-27 at 3 52 34 PM

In mTLS, both the client and server have a certificate, and both sides authenticate using their public/private key pair.
Steps:

  1. Client connects to server
  2. Server presents its TLS certificate
  3. Client verifies the server's certificate
  4. Client presents its TLS certificate
  5. Server verifies the client's certificate
  6. Server grants access
  7. Client and server exchange information over encrypted TLS connection

Testing Scenarios:
Screenshot 2025-10-22 at 2 19 09 PM


---

## How mTLS Works
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 good writing!


---

## Complete Working Example
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe add another section of How to enable mTLS?


## Complete Working Example

For a complete working example with detailed code and configuration, refer to the [helloworld_tls sample](https://github.com/cadence-workflow/cadence-samples/tree/master/new_samples/client_samples/helloworld_tls) in the Cadence samples repository. This sample demonstrates how to:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you update the samples change explaining how this command works?
./cadence-server --env development --zone tls start

│ All subsequent data is encrypted │
│ │
```

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a section here explaining how mTLS works with Cadence, explaining creating gRPC options, then the gRPC transport object and Cadence using it (how client is initialized). Leave links to the sample changes and the client repo.
Similarly please leave pointers to server code, explaining how a secure server is started.

@vishwa-uber vishwa-uber merged commit fe0f768 into cadence-workflow:master Nov 1, 2025
4 checks passed
@vishwa-uber vishwa-uber deleted the mutual_tls_doc branch November 1, 2025 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants